<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered)">
<title>Effective Dating</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"Arial Black";
	panose-1:2 11 10 4 2 1 2 2 2 4;}
@font-face
	{font-family:GillSans;}
@font-face
	{font-family:Copperplate31ab;}
@font-face
	{font-family:"Verdana\, Arial\, Helvetica";}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	font-size:11.0pt;
	font-family:Arial;}
h1
	{margin-top:24.0pt;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.3in;
	page-break-after:avoid;
	font-size:14.0pt;
	font-family:Copperplate31ab;
	font-weight:normal;}
h2
	{margin-top:.25in;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.4in;
	text-indent:-.4in;
	page-break-after:avoid;
	layout-grid-mode:char;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:bold;
	font-style:italic;}
h3
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.5in;
	text-indent:-.5in;
	page-break-after:avoid;
	layout-grid-mode:char;
	font-size:10.0pt;
	font-family:Arial;
	font-weight:bold;}
h4
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:0in;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:bold;}
h5
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.7in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.7in;
	page-break-after:avoid;
	punctuation-wrap:simple;
	text-autospace:none;
	font-size:12.0pt;
	font-family:GillSans;
	font-weight:bold;}
h6
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.8in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.8in;
	font-size:11.0pt;
	font-family:GillSans;
	font-weight:bold;}
p.MsoHeading7, li.MsoHeading7, div.MsoHeading7
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.9in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.9in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoHeading8, li.MsoHeading8, div.MsoHeading8
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:1.0in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-1.0in;
	font-size:12.0pt;
	font-family:GillSans;
	font-style:italic;}
p.MsoHeading9, li.MsoHeading9, div.MsoHeading9
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:1.1in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-1.1in;
	font-size:11.0pt;
	font-family:Arial;}
p.MsoIndex1, li.MsoIndex1, div.MsoIndex1
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:12.0pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-12.0pt;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoIndex2, li.MsoIndex2, div.MsoIndex2
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:24.0pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-12.0pt;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoIndex3, li.MsoIndex3, div.MsoIndex3
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.5in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-12.0pt;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoIndex4, li.MsoIndex4, div.MsoIndex4
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:48.0pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-12.0pt;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoIndex5, li.MsoIndex5, div.MsoIndex5
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:60.0pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-12.0pt;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoIndex6, li.MsoIndex6, div.MsoIndex6
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:1.0in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-12.0pt;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoIndex7, li.MsoIndex7, div.MsoIndex7
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:84.0pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-12.0pt;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoIndex8, li.MsoIndex8, div.MsoIndex8
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:96.0pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-12.0pt;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoIndex9, li.MsoIndex9, div.MsoIndex9
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:1.5in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-12.0pt;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoToc1, li.MsoToc1, div.MsoToc1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Times New Roman";
	font-weight:bold;}
p.MsoToc2, li.MsoToc2, div.MsoToc2
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:11.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Times New Roman";
	font-style:italic;}
p.MsoToc3, li.MsoToc3, div.MsoToc3
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:22.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Times New Roman";}
p.MsoToc4, li.MsoToc4, div.MsoToc4
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:33.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Times New Roman";}
p.MsoToc5, li.MsoToc5, div.MsoToc5
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:44.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Times New Roman";}
p.MsoToc6, li.MsoToc6, div.MsoToc6
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:55.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Times New Roman";}
p.MsoToc7, li.MsoToc7, div.MsoToc7
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:66.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Times New Roman";}
p.MsoToc8, li.MsoToc8, div.MsoToc8
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:77.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Times New Roman";}
p.MsoToc9, li.MsoToc9, div.MsoToc9
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:88.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Times New Roman";}
p.MsoNormalIndent, li.MsoNormalIndent, div.MsoNormalIndent
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.5in;
	font-size:11.0pt;
	font-family:Arial;}
p.MsoFootnoteText, li.MsoFootnoteText, div.MsoFootnoteText
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:11.0pt;
	font-family:GillSans;}
p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:11.0pt;
	font-family:GillSans;}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:11.0pt;
	font-family:GillSans;}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:11.0pt;
	font-family:GillSans;}
p.MsoIndexHeading, li.MsoIndexHeading, div.MsoIndexHeading
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:bold;}
p.MsoCaption, li.MsoCaption, div.MsoCaption
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:center;
	font-size:12.0pt;
	font-family:GillSans;
	font-weight:bold;}
p.MsoTof, li.MsoTof, div.MsoTof
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:24.0pt;
	text-indent:-24.0pt;
	font-size:11.0pt;
	font-family:Arial;}
p.MsoEnvelopeAddress, li.MsoEnvelopeAddress, div.MsoEnvelopeAddress
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:2.0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:12.0pt;
	font-family:Arial;}
p.MsoEnvelopeReturn, li.MsoEnvelopeReturn, div.MsoEnvelopeReturn
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:11.0pt;
	font-family:Arial;}
span.MsoFootnoteReference
	{vertical-align:super;}
span.MsoCommentReference
	{color:fuchsia;}
p.MsoEndnoteText, li.MsoEndnoteText, div.MsoEndnoteText
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:11.0pt;
	font-family:GillSans;}
p.MsoToa, li.MsoToa, div.MsoToa
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:12.0pt;
	text-indent:-12.0pt;
	font-size:11.0pt;
	font-family:Arial;}
p.MsoMacroText, li.MsoMacroText, div.MsoMacroText
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoToaHeading, li.MsoToaHeading, div.MsoToaHeading
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	font-size:11.0pt;
	font-family:Arial;
	font-weight:bold;}
p.MsoList, li.MsoList, div.MsoList
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.25in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoListBullet, li.MsoListBullet, div.MsoListBullet
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.25in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoListNumber, li.MsoListNumber, div.MsoListNumber
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.25in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoList2, li.MsoList2, div.MsoList2
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.5in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoList3, li.MsoList3, div.MsoList3
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.75in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoList4, li.MsoList4, div.MsoList4
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:1.0in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoList5, li.MsoList5, div.MsoList5
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:1.25in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoListBullet2, li.MsoListBullet2, div.MsoListBullet2
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.5in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoListBullet3, li.MsoListBullet3, div.MsoListBullet3
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.75in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoListBullet4, li.MsoListBullet4, div.MsoListBullet4
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:1.0in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoListBullet5, li.MsoListBullet5, div.MsoListBullet5
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:1.25in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoListNumber2, li.MsoListNumber2, div.MsoListNumber2
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.5in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoListNumber3, li.MsoListNumber3, div.MsoListNumber3
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.75in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoListNumber4, li.MsoListNumber4, div.MsoListNumber4
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:1.0in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoListNumber5, li.MsoListNumber5, div.MsoListNumber5
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:1.25in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoTitle, li.MsoTitle, div.MsoTitle
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	font-size:18.0pt;
	font-family:Arial;
	color:navy;
	font-weight:bold;}
p.MsoClosing, li.MsoClosing, div.MsoClosing
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:3.0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoSignature, li.MsoSignature, div.MsoSignature
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:3.0in;
	font-size:11.0pt;
	font-family:Arial;}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	layout-grid-mode:char;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoBodyTextIndent, li.MsoBodyTextIndent, div.MsoBodyTextIndent
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.25in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoListContinue, li.MsoListContinue, div.MsoListContinue
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.25in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoListContinue2, li.MsoListContinue2, div.MsoListContinue2
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.5in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoListContinue3, li.MsoListContinue3, div.MsoListContinue3
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.75in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoListContinue4, li.MsoListContinue4, div.MsoListContinue4
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:1.0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoListContinue5, li.MsoListContinue5, div.MsoListContinue5
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:1.25in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoMessageHeader, li.MsoMessageHeader, div.MsoMessageHeader
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.75in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.75in;
	background:#CCCCCC;
	font-size:12.0pt;
	font-family:Arial;}
p.MsoSubtitle, li.MsoSubtitle, div.MsoSubtitle
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:14.0pt;
	font-family:Copperplate31ab;
	font-weight:bold;}
p.MsoSalutation, li.MsoSalutation, div.MsoSalutation
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	font-size:11.0pt;
	font-family:Arial;}
p.MsoDate, li.MsoDate, div.MsoDate
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoBodyTextFirstIndent, li.MsoBodyTextFirstIndent, div.MsoBodyTextFirstIndent
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:10.5pt;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoBodyTextFirstIndent2, li.MsoBodyTextFirstIndent2, div.MsoBodyTextFirstIndent2
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.25in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:10.5pt;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoNoteHeading, li.MsoNoteHeading, div.MsoNoteHeading
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	font-size:11.0pt;
	font-family:Arial;}
p.MsoBodyText2, li.MsoBodyText2, div.MsoBodyText2
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	line-height:200%;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoBodyText3, li.MsoBodyText3, div.MsoBodyText3
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	line-height:200%;
	font-size:12.0pt;
	font-family:Arial;}
p.MsoBodyTextIndent2, li.MsoBodyTextIndent2, div.MsoBodyTextIndent2
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.25in;
	text-align:justify;
	text-justify:inter-ideograph;
	line-height:200%;
	font-size:12.0pt;
	font-family:GillSans;}
p.MsoBodyTextIndent3, li.MsoBodyTextIndent3, div.MsoBodyTextIndent3
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.25in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:8.0pt;
	font-family:GillSans;}
p.MsoBlockText, li.MsoBlockText, div.MsoBlockText
	{margin-top:6.0pt;
	margin-right:1.0in;
	margin-bottom:6.0pt;
	margin-left:1.0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:12.0pt;
	font-family:GillSans;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:none none;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:none none;}
p.MsoDocumentMap, li.MsoDocumentMap, div.MsoDocumentMap
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	background:navy;
	font-size:12.0pt;
	font-family:Tahoma;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:12.0pt;
	font-family:GillSans;}
p
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Times New Roman";}
address
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:12.0pt;
	font-family:GillSans;
	font-style:italic;}
pre
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:11.0pt;
	font-family:"Courier New";}
p.xml, li.xml, div.xml
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Courier New";}
p.appendices, li.appendices, div.appendices
	{margin-top:24.0pt;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	text-align:center;
	text-indent:-.3in;
	page-break-after:avoid;
	font-size:14.0pt;
	font-family:Copperplate31ab;
	font-weight:bold;}
p.bullet, li.bullet, div.bullet
	{margin-top:3.0pt;
	margin-right:4.3pt;
	margin-bottom:3.0pt;
	margin-left:.5in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	layout-grid-mode:char;
	font-size:12.0pt;
	font-family:GillSans;}
p.footerlandscape, li.footerlandscape, div.footerlandscape
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:11.0pt;
	font-family:GillSans;}
p.headerlandscape, li.headerlandscape, div.headerlandscape
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:11.0pt;
	font-family:GillSans;}
p.number, li.number, div.number
	{margin-top:3.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.5in;
	text-indent:-.25in;
	font-size:11.0pt;
	font-family:Arial;}
p.titlecover, li.titlecover, div.titlecover
	{margin-top:1.25in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.75in;
	margin-bottom:.0001pt;
	page-break-after:avoid;
	font-size:36.0pt;
	font-family:Arial;
	letter-spacing:-2.4pt;
	font-weight:bold;}
p.subtitlecover, li.subtitlecover, div.subtitlecover
	{margin-top:76.0pt;
	margin-right:84.0pt;
	margin-bottom:0in;
	margin-left:.75in;
	margin-bottom:.0001pt;
	page-break-after:avoid;
	font-size:20.0pt;
	font-family:"Times New Roman";
	letter-spacing:-1.0pt;
	font-style:italic;}
p.tabletext, li.tabletext, div.tabletext
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Arial;}
p.tablebullet, li.tablebullet, div.tablebullet
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.15in;
	margin-bottom:.0001pt;
	text-indent:-.15in;
	font-size:11.0pt;
	font-family:Arial;}
p.tableheader, li.tableheader, div.tableheader
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:11.0pt;
	font-family:Copperplate31ab;
	color:white;
	font-weight:bold;}
p.tablelist, li.tablelist, div.tablelist
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.25in;
	margin-bottom:.0001pt;
	text-indent:-.3in;
	font-size:11.0pt;
	font-family:Arial;}
p.tablesubheader, li.tablesubheader, div.tablesubheader
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:11.0pt;
	font-family:Arial;
	font-weight:bold;}
p.version, li.version, div.version
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:10.0pt;
	font-family:Copperplate31ab;}
p.style1, li.style1, div.style1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:.5in;
	text-indent:-.5in;
	page-break-after:avoid;
	layout-grid-mode:char;
	font-size:10.0pt;
	font-family:Arial;
	font-weight:bold;}
p.h4, li.h4, div.h4
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	font-size:11.0pt;
	font-family:Arial;
	font-weight:bold;}
p.b, li.b, div.b
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";
	color:red;
	font-weight:bold;}
p.e, li.e, div.e
	{margin-top:0in;
	margin-right:12.0pt;
	margin-bottom:0in;
	margin-left:12.0pt;
	margin-bottom:.0001pt;
	text-indent:-12.0pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.k, li.k, div.k
	{margin-top:0in;
	margin-right:12.0pt;
	margin-bottom:0in;
	margin-left:12.0pt;
	margin-bottom:.0001pt;
	text-indent:-12.0pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.t, li.t, div.t
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:#990000;}
p.xt, li.xt, div.xt
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:#990099;}
p.ns, li.ns, div.ns
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:red;}
p.m, li.m, div.m
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:blue;}
p.tx, li.tx, div.tx
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	font-weight:bold;}
p.db, li.db, div.db
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:12.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:Courier;}
p.di, li.di, div.di
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:Courier;}
p.d, li.d, div.d
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:blue;}
p.pi, li.pi, div.pi
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:blue;}
p.cb, li.cb, div.cb
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:12.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:Courier;
	color:#888888;}
p.ci, li.ci, div.ci
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:Courier;
	color:#888888;}
p.workingdraftdate, li.workingdraftdate, div.workingdraftdate
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:0in;
	font-size:16.0pt;
	font-family:Arial;
	color:navy;}
p.heading3preface, li.heading3preface, div.heading3preface
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:Arial;
	font-weight:bold;}
p.prefacetext, li.prefacetext, div.prefacetext
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:Arial;}
p.heading2preface, li.heading2preface, div.heading2preface
	{margin-top:24.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:0in;
	font-size:14.0pt;
	font-family:Arial;
	color:navy;
	font-weight:bold;}
p.tabletext0, li.tabletext0, div.tabletext0
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:Arial;}
span.m1
	{color:blue;}
span.pi1
	{color:blue;}
span.d1
	{color:blue;}
span.b1
	{font-family:"Courier New";
	color:red;
	font-weight:bold;
	text-decoration:none none;}
span.t1
	{color:#990000;}
span.tx1
	{font-weight:bold;}
span.note1
	{color:gray;}
span.headers1
	{font-family:"Verdana\, Arial\, Helvetica";
	font-weight:bold;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in .6in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><img width=281 height=87
src="EffectiveDating_files/image001.jpg">&nbsp;&nbsp; </p>

<p class=MsoTitle>Effective Dating </p>

<p class=MsoTitle>Recommendation, 2007 April 15</p>

<p class=heading3preface style='margin-top:6.0pt'>Editor:</p>

<p class=prefacetext>Karl Brophey, eBenX</p>

<p class=heading3preface style='margin-top:6.0pt'>Authors:</p>

<p class=prefacetext>Mark Marsden, Ultimate Software</p>

<p class=prefacetext>Karl Brophey, eBenX</p>

<p class=heading3preface style='margin-top:6.0pt'>Contributors:</p>

<p class=prefacetext>Members of the Cross Process Objects workgroup</p>

<p class=prefacetext style='margin-left:0in'><b>&nbsp;</b></p>

<p class=prefacetext style='margin-left:0in'><b>Copyright &copy; 2007 HR-XML
Consortium, Inc.</b></p>

<p class=prefacetext>&nbsp; </p>

<div style='border:none;border-top:double windowtext 2.25pt;padding:24.0pt 0in 0in 0in'>

<p class=heading2preface style='margin-top:12.0pt'>Abstract</p>

</div>

<p class=MsoPlainText><span style='font-family:Arial'>Effective Dating may be
relevant for objects, associations between objects and single attributes of
objects.&nbsp; The objective of this document is to define a consistent manner
for using effective dates for all of these situations throughout the
consortium&#8217;s work. Specifically, this will consist of a guided thought
process for work groups to follow to determine their needs as well as a set of
design patterns to be used based on the decisions made.</span></p>

<b><span style='font-size:14.0pt;font-family:Arial;color:navy'><br clear=all
style='page-break-before:always'>
</span></b>

<p class=heading2preface style='margin-top:12.0pt;margin-right:0in;margin-bottom:
0in;margin-left:0in;margin-bottom:.0001pt'>Table of Contents</p>

<p class=MsoToc1><span class=MsoHyperlink><a href="#_Toc79313709">1<span
style='font-size:12.0pt;color:windowtext;font-weight:normal'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Overview<span style='color:windowtext;display:none'>.. 3</span></a></span></p>

<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc79313710">1.1<span
style='font-size:12.0pt;color:windowtext;font-style:normal'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Objective<span style='color:windowtext;display:none'>. 3</span></a></span></p>

<p class=MsoToc3><span class=MsoHyperlink><a href="#_Toc79313711">1.1.1<span
style='font-size:12.0pt;color:windowtext'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Domain Issues<span style='color:windowtext;display:none'>. 3</span></a></span></p>

<p class=MsoToc3><span class=MsoHyperlink><a href="#_Toc79313712">1.1.2<span
style='font-size:12.0pt;color:windowtext'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Business Reasons<span style='color:windowtext;display:none'>. 4</span></a></span></p>

<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc79313713">1.2<span
style='font-size:12.0pt;color:windowtext;font-style:normal'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Design Requirements<span style='color:windowtext;display:none'>. 4</span></a></span></p>

<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc79313714">1.3<span
style='font-size:12.0pt;color:windowtext;font-style:normal'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Scope<span style='color:windowtext;display:none'>. 4</span></a></span></p>

<p class=MsoToc3><span class=MsoHyperlink><a href="#_Toc79313715">1.3.1<span
style='font-size:12.0pt;color:windowtext'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Major Components<span style='color:windowtext;display:none'>. 4</span></a></span></p>

<p class=MsoToc3><span class=MsoHyperlink><a href="#_Toc79313716">1.3.2<span
style='font-size:12.0pt;color:windowtext'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Items Within the Design Scope<span style='color:windowtext;display:none'>.
4</span></a></span></p>

<p class=MsoToc3><span class=MsoHyperlink><a href="#_Toc79313717">1.3.3<span
style='font-size:12.0pt;color:windowtext'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Items Outside of Design Scope<span style='color:windowtext;display:none'>.
5</span></a></span></p>

<p class=MsoToc1><span class=MsoHyperlink><a href="#_Toc79313718">2<span
style='font-size:12.0pt;color:windowtext;font-weight:normal'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Implementation Considerations<span style='color:windowtext;display:none'>.
6</span></a></span></p>

<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc79313719">2.1<span
style='font-size:12.0pt;color:windowtext;font-style:normal'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Overview<span style='color:windowtext;display:none'>.. 6</span></a></span></p>

<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc79313720">2.2<span
style='font-size:12.0pt;color:windowtext;font-style:normal'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Identifying Situations for &#8220;Event Dates&#8221;<span
style='color:windowtext;display:none'>. 6</span></a></span></p>

<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc79313721">2.3<span
style='font-size:12.0pt;color:windowtext;font-style:normal'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Handling Situations for &#8220;Event Dates&#8221;<span style='color:
windowtext;display:none'>. 6</span></a></span></p>

<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc79313722">2.4<span
style='font-size:12.0pt;color:windowtext;font-style:normal'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Identifying Situations for &#8220;Applying to State&#8221;<span
style='color:windowtext;display:none'>. 7</span></a></span></p>

<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc79313723">2.5<span
style='font-size:12.0pt;color:windowtext;font-style:normal'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Handling Situations for &#8220;Applying to State&#8221;<span
style='color:windowtext;display:none'>. 7</span></a></span></p>

<p class=MsoToc3><span class=MsoHyperlink><a href="#_Toc79313724">2.5.1<span
style='font-size:12.0pt;color:windowtext'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Representation of the Dates<span style='color:windowtext;display:none'>.
7</span></a></span></p>

<p class=MsoToc3><span class=MsoHyperlink><a href="#_Toc79313725">2.5.2<span
style='font-size:12.0pt;color:windowtext'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Positioning within the Model<span style='color:windowtext;display:none'>
7</span></a></span></p>

<p class=MsoToc3><span class=MsoHyperlink><a href="#_Toc79313726">2.5.3<span
style='font-size:12.0pt;color:windowtext'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Allowance for Multiple States<span style='color:windowtext;display:none'>.
8</span></a></span></p>

<p class=MsoToc3><span class=MsoHyperlink><a href="#_Toc79313727">2.5.4<span
style='font-size:12.0pt;color:windowtext'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Correction<span style='color:windowtext;display:none'>. 8</span></a></span></p>

<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc79313728">2.6<span
style='font-size:12.0pt;color:windowtext;font-style:normal'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Providing Implementation Guide Documentation<span style='color:windowtext;
display:none'>. 8</span></a></span></p>

<p class=MsoToc1><span class=MsoHyperlink><a href="#_Toc79313729">3<span
style='font-size:12.0pt;color:windowtext;font-weight:normal'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Appendix A - Vocabulary Requirements<span style='color:windowtext;
display:none'>. 9</span></a></span></p>

<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc79313730">3.1<span
style='font-size:12.0pt;color:windowtext;font-style:normal'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Overview<span style='color:windowtext;display:none'>.. 9</span></a></span></p>

<p class=MsoToc3><span class=MsoHyperlink><a href="#_Toc79313731">3.1.1<span
style='font-size:12.0pt;color:windowtext'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>&#8220;Dating Scope&#8221;<span style='color:windowtext;display:none'>.
9</span></a></span></p>

<p class=MsoToc3><span class=MsoHyperlink><a href="#_Toc79313732">3.1.2<span
style='font-size:12.0pt;color:windowtext'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>&#8220;Dating Character&#8221;<span style='color:windowtext;display:
none'>. 10</span></a></span></p>

<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc79313733">3.2<span
style='font-size:12.0pt;color:windowtext;font-style:normal'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Definitions<span style='color:windowtext;display:none'>. 10</span></a></span></p>

<p class=MsoToc1><span class=MsoHyperlink><a href="#_Toc79313734">4<span
style='font-size:12.0pt;color:windowtext;font-weight:normal'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Appendix B - Document Version History<span style='color:windowtext;
display:none'>. 13</span></a></span></p>

<p class=MsoToc1><span class=MsoHyperlink><a href="#_Toc79313735">5<span
style='font-size:12.0pt;color:windowtext;font-weight:normal'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Appendix C &#8211; Related Documents<span style='color:windowtext;
display:none'>. 13</span></a></span></p>

<p class=MsoToc1><span class=MsoHyperlink><a href="#_Toc79313736">6<span
style='font-size:12.0pt;color:windowtext;font-weight:normal'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Appendix C &#8211; Reference Examples<span style='color:windowtext;
display:none'>. 14</span></a></span></p>

<p class=MsoToc1>&nbsp;</p>

<span style='font-size:14.0pt;font-family:Copperplate31ab'><br clear=all
style='page-break-before:always'>
</span>

<h1><a name="_Toc79313709">1</a><span style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Overview<a name="_Toc492656056"></a><a name="_Toc492655894"></a><a
name="_Toc493472395"></a><a name="_Toc493472734"></a><a name="_Toc493472396"></a><a
name="_Toc493472735"></a><a name="_Toc493472034"></a><a name="_Toc493472399"></a><a
name="_Toc493472738"></a><a name="_Toc493472400"></a><a name="_Toc493472739"></a><a
name="_Toc493472401"></a><a name="_Toc493472740"></a><a name="_Toc493472436"></a><a
name="_Toc493472775"></a><a name="_Toc493472437"></a><a name="_Toc493472776"></a><a
name="_Toc492655893"></a><a name="_Toc492656055"></a><a name="_Toc493472438"></a><a
name="_Toc493472777"></a></h1>

<h2><a name="_Toc79313710">1.1</a><span style='font-size:7.0pt;font-family:
"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Objective</h2>

<p class=MsoNormal>Effective Dating may be relevant for objects, associations
between objects and single attributes of objects.&nbsp; The objective of this
document is to define a consistent manner for using effective dates for all of
these situations throughout the consortium&#8217;s work. Specifically, this
will consist of a guided thought process for work groups to follow to determine
their needs as well as a set of design patterns to be used based on the
decisions made.<span style='color:blue'> </span></p>

<h3><a name="_Toc79313711">1.1.1</a><span style='font-size:7.0pt;font-family:
"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Domain
Issues</h3>

<p class=MsoNormal>Effective dating within the Human Resource domain poses many
challenges. Although many situations only require a date, some circumstances need
precision to the second or more. For example, a medical insurance policy may be
effective on 2001-01-01 at 00:01:01 EST. If an employee used medical services
prior to that time, they may not be covered.</p>

<p class=MsoNormal>Given the scope of effective dating, we need to develop a
consistent method for understanding and transmitting such dates. Although this
document is not intended to address how to handle specific data situations
within HR, some of the major areas of concern that drive the need to have a
consistent handling of effective dating are listed below: </p>

<p class=MsoNormal style='margin-left:.75in;text-indent:-.25in'>1.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Contact information, such as phone, address, and name are particularly
date sensitive. A person may have a summer home address and a winter home
address that both need to be tracked.</p>

<p class=MsoNormal style='margin-left:.75in;text-indent:-.25in'>2.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Positions are typically budgeted for a period of time, such as a fiscal
or calendar year.</p>

<p class=MsoNormal style='margin-left:.75in;text-indent:-.25in'>3.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Pay grades are effective for a specified time frame. A company may
create new pay grades that won&#8217;t be effective until the next fiscal year.</p>

<p class=MsoNormal style='margin-left:.75in;text-indent:-.25in'>4.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Employee training and development may be date sensitive, such as
certification expiration dates. </p>

<p class=MsoNormal style='margin-left:.75in;text-indent:-.25in'>5.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Participation dates for benefits are date and time sensitive. An
employer may need to track original hire date, start date, leave of absence,
termination, and recall dates to determine participation or breaks in coverage.</p>

<p class=MsoNormal style='margin-left:.75in;text-indent:-.25in'>6.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Compensation and time accounting rely heavily on effective dating. If an
employee&#8217;s pay changed in the middle of a pay cycle and/or retroactively,
the company needs a method for calculating the correct pay.</p>

<p class=MsoNormal style='margin-left:.75in;text-indent:-.25in'>7.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Companies use effective dating to track employee history of departments,
positions, affiliations, and the like. </p>

<p class=MsoNormal style='margin-left:.75in;text-indent:-.25in'>8.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Staffing may require contracts for vendor employees that are effective
for a specified time frame. </p>

<p class=MsoNormal style='margin-left:.75in;text-indent:-.25in'>9.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Employee scheduling requires date and time manipulation. </p>

<p class=MsoNormal style='margin-left:.75in;text-indent:-.25in'>10.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp; </span>Requisitions
are usually active for a period of time.&nbsp; If an employee is unable to fill
the position within that timeframe, they may extend the date or remove the
requisition.</p>

<p class=MsoNormal style='margin-left:.75in;text-indent:-.25in'>11.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp; </span>Like
compensation, benefits providers frequently require precise dating, including
considerations of retroactivity, to provide fair and accurate provision of
services.</p>

<h3><a name="_Toc79313712">1.1.2</a><span style='font-size:7.0pt;font-family:
"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Business
Reasons</h3>

<p class=MsoNormal>Almost all HR and Payroll business processes revolve around
some event or string of events in time. All of these events have in common a
start point, an end point, a duration, or some combination of these, that must
be represented in a format that can be efficiently stored, conveyed and
processed by HRIS systems.&nbsp; By developing a standard approach to providing
date information we will prevent the necessity of other HR-XML Consortium work
groups from devoting time and effort to addressing this on a case-by-case
basis.</p>

<h2><a name="_Toc79313713">1.2</a><span style='font-size:7.0pt;font-family:
"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Design
Requirements</h2>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><a
name="_Toc492655895"></a><a name="_Toc492656057"></a>The Design requirements
must take into account the following:</p>

<p class=MsoNormal style='margin-top:0in;margin-right:0in;margin-bottom:0in;
margin-left:.25in;margin-bottom:.0001pt;text-indent:-.25in'>1.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>The global concept of time as described in the <i>DateTime Data Types. </i></p>

<p class=MsoNormal style='margin-top:0in;margin-right:0in;margin-bottom:0in;
margin-left:.25in;margin-bottom:.0001pt;text-indent:-.25in'><i>2.</i><i><span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></i>Representing Date and Time values in Schema and in DTD as presented
in the <i>DateTime Data Types. </i></p>

<p class=MsoNormal style='margin-top:0in;margin-right:0in;margin-bottom:0in;
margin-left:.25in;margin-bottom:.0001pt;text-indent:-.25in'>3.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>How to determine where and when to use effective dating in a Schema/DTD
design</p>

<h2><a name="_Toc79313714">1.3</a><span style='font-size:7.0pt;font-family:
"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Scope</h2>

<h3><a name="_Toc79313715">1.3.1</a><span style='font-size:7.0pt;font-family:
"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Major
Components</h3>

<p class=MsoNormal>Deliver a standard representation of effective dating,
regardless of where used.&nbsp; The goal is consistency.&nbsp; </p>

<p class=MsoNormal>Provide a yardstick that the CPO can use as a basis for
reviewing other workgroup&#8217;s schema designs.</p>

<h3><a name="_Toc517164389"></a><a name="_Toc79313716"></a>1.3.2<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Items Within the Design Scope</h3>

<p class=MsoNormal>We first create a clear, concise vernacular for discussing
effective dating. We can then provide standard usage guidelines for:</p>

<p class=MsoNormal style='margin-left:.25in;text-indent:-.25in'>1.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>When to use Transaction Date/Time vs. Effective Date/Time</p>

<p class=MsoNormal style='margin-left:.25in;text-indent:-.25in'>2.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>How to determine the granularity required for effective dating</p>

<p class=MsoNormal style='margin-left:.25in;text-indent:-.25in'>3.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>How to use Effective Dating with different types of processes, <br>
i.e. Inserts vs. Modifications</p>

<p class=MsoNormal style='margin-left:.25in;text-indent:-.25in'>4.<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>When to use the various types in the <i>DateTime Data Types </i>when
applying effective and transaction dating.</p>

<h3><a name="_Toc79313717">1.3.3</a><span style='font-size:7.0pt;font-family:
"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Items
Outside of Design Scope</h3>

<p class=MsoNormal>While it may be necessary to review object models and how
effective dates might be stored, the storage of effective dates within any
single specific HR sub-domain is outside the scope of this document. That is,
this document does not attempt to describe a universe of specific event dates,
such as Pay Date, Birth Date, etc.&nbsp; These data elements are specific to
the business process being described and fall outside the scope of this
document. Instead, a consistent approach to the treatment of such data elements
is put forth in the form of a set of guidelines.</p>

<p class=MsoNormal>Time scheduling rules, such as &#8216;7 days before
Christmas&#8217; are not addressed in this document. Likewise scheduling items
of the form &#8216;Every Tuesday at 10:00AM&#8217; or &#8216;Every Monday
through Friday from 3:30PM to 4:00PM&#8217; is not addressed in this document.
It is encouraged that for these needs that the relevant schema data types be
used when possible.</p>

<p class=MsoNormal>The topic of concepts such as change reason is left to the
workgroups or other CPO projects. While there is some correlation between why
you would have a new effective date and a change reason, the variety on the
topic is more than this scope can take on. Look to the Events workgroup for
another voice on the topic.</p>

<span style='font-size:14.0pt;font-family:Copperplate31ab'><br clear=all
style='page-break-before:always'>
</span>

<h1><a name="_Toc493471746"></a><a name="_Toc493472043"></a><a
name="_Toc493472446"></a><a name="_Toc493472785"></a><a name="_Toc493471751"></a><a
name="_Toc493472048"></a><a name="_Toc493472451"></a><a name="_Toc493472790"></a><a
name="_Toc493471752"></a><a name="_Toc493472049"></a><a name="_Toc493472452"></a><a
name="_Toc493472791"></a><a name="_Toc493471754"></a><a name="_Toc493472051"></a><a
name="_Toc493472454"></a><a name="_Toc493472793"></a><a name="_Toc492655903"></a><a
name="_Toc492656065"></a><a name="_Toc492868751"></a><a name="_Toc492868858"></a><a
name="_Toc493463955"></a><a name="_Toc493471755"></a><a name="_Toc493472052"></a><a
name="_Toc493472455"></a><a name="_Toc493472794"></a><a name="_Toc492655904"></a><a
name="_Toc492656066"></a><a name="_Toc492868752"></a><a name="_Toc492868859"></a><a
name="_Toc493463956"></a><a name="_Toc493471756"></a><a name="_Toc493472053"></a><a
name="_Toc493472456"></a><a name="_Toc493472795"></a><a name="_Toc493471757"></a><a
name="_Toc493472054"></a><a name="_Toc493472457"></a><a name="_Toc493472796"></a><a
name="_Toc492655909"></a><a name="_Toc492656071"></a><a name="_Toc492868757"></a><a
name="_Toc492868864"></a><a name="_Toc493463961"></a><a name="_Toc493471761"></a><a
name="_Toc493472058"></a><a name="_Toc493472461"></a><a name="_Toc493472800"></a><a
name="_Toc492655914"></a><a name="_Toc492656076"></a><a name="_Toc492868762"></a><a
name="_Toc492868869"></a><a name="_Toc493463966"></a><a name="_Toc493471766"></a><a
name="_Toc493472063"></a><a name="_Toc493472466"></a><a name="_Toc493472805"></a><a
name="_Toc492655917"></a><a name="_Toc492656079"></a><a name="_Toc492868765"></a><a
name="_Toc492868872"></a><a name="_Toc493463969"></a><a name="_Toc493471769"></a><a
name="_Toc493472066"></a><a name="_Toc493472469"></a><a name="_Toc493472808"></a>2<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>&nbsp;<a name="_Toc79313718">Implementation Considerations</a></h1>

<p class=xml><i><span style='font-family:Arial'>Before reading this section,
you should be completely familiar the terminology put forth in Chapter 3
Vocabulary Requirements. </span></i></p>

<h2><a name="_Toc517164397"></a><a name="_Toc79313719"></a>2.1<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Overview</h2>

<p class=xml><span style='font-family:Arial'>As any group works towards
establishing a design for transmission of data, they will encounter date and/or
dateTime elements they wish to include. As pointed out earlier, when a date is
included it is always a description of an event or a state. As such, this
document can provide guidance on how to handle and model all of these elements.
Deciding what events and states should have date information included is left
solely to the individual designers however.</span></p>

<p class=xml><span style='font-family:Arial'>Once a list of events and states
has been identified, several decisions must be made. First and foremost is
whether this is a representation of an event or a state. You must also decide
which of the various data types is appropriate, as detailed in the Date and
Time Data Types document, deciding between date or dateTime, global, local or
either, and whether to allow &#8220;not known&#8221; and/or &#8220;not
applicable&#8221; values. Finally, if your representation is of state, you must
choose the specific representation strategy you will employ and understand how
you will handle representations of multiple states through time, correction,
and a state that is found to be &#8220;never in force&#8221;.</span></p>

<h2><a name="_Toc517164398"></a><a name="_Toc79313720"></a>2.2<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Identifying Situations for &#8220;Event Dates&#8221;</h2>

<p class=xml><span style='font-family:Arial'>For identifying those items you
wish to treat as &#8220;event dates&#8221;, some will be obvious&#8212;one time
only events whose occurrence is significant within the HR domain. Examples
would be a birth date, a graduation date, and a certification date. Events that
mark the beginning or end of a particular state might be treated with dates as
&#8220;applying to state&#8221;, or they could be treated as events, or both.
If the occurrence of the event will tend to be relevant, even after the
immediate state that would share a date with the event has changed, a separate
element for the &#8220;event date&#8221; should be created. Examples of this
form would be a hire date, a retirement date, and a date that shows the
original date of continuous coverage for a particular benefit plan.</span></p>

<h2><a name="_Toc517164399"></a><a name="_Toc79313721"></a>2.3<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Handling Situations for &#8220;Event Dates&#8221;</h2>

<p class=xml><span style='font-family:Arial'>If you choose to represent an
&#8220;event date&#8221;, you should choose a specific, descriptive name of the
form <b><i>Event</i>Date</b> where &#8220;<i>Event</i>&#8221; is a suitable
name for the event. Coordination of these names between layouts, if done, will
be handled via the Consortium glossary.</span></p>

<p class=xml><span style='font-family:Arial'>The location of such a data
element is left to the discretion of the designers. In essence they behave like
any other attribute of an object or relationship. Likewise, the decision on
utilizing an XML element or attribute is left to the designers with the
guidance of other Consortia guideline documents.</span></p>

<p class=xml><span style='font-family:Arial'>As discussed elsewhere in this
document, &#8220;event dates&#8221; are relatively simple to handle corrections
upon, as they simply require a new transmission containing the corrected
values.</span></p>

<h2><a name="_Toc517164400"></a><a name="_Toc79313722"></a>2.4<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Identifying Situations for &#8220;Applying to State&#8221;</h2>

<p class=MsoNormal>As discussed above, virtually any call for a date that does
not fit as an &#8220;event date&#8221; will by a situation that should be
viewed as a representation of state through time. The most typical case will be
when there is a &#8220;snap-shot&#8221; of information describing an employee,
a benefit, or a job posting, and it must be known for what period of time the
representation is valid.</p>

<h2><a name="_Toc517164401"></a><a name="_Toc79313723"></a>2.5<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Handling Situations for &#8220;Applying to State&#8221;</h2>

<p class=MsoNormal>As a designer, once you have decided you need dates to
&#8220;apply to state&#8221;, you must clearly resolve what representations of
state in your design need to be described with dates. You must then decide upon
a start and end approach, or a series of states each having a start date only.
Finally, consider correction, including a state that was &#8220;Never in
Force&#8221;. </p>

<h3><a name="_Toc517164402"></a><a name="_Toc79313724"></a>2.5.1<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Representation of the Dates </h3>

<p class=MsoNormal>While the next section will discuss the detail of where to
place the dates within a particular model, how you place the dates will always
be identical. Either a pair of attributes or elements (as deemed most
appropriate in the design based on any other applicable Consortia documents)
with the set names of <b>StartDate</b> and <b>EndDate</b> should be inserted as
appropriate; If the series of states approach is preferred, a single element or
attribute named <b>StartDate</b>.</p>

<p class=MsoNormal>The specific data type should be chosen based on the
guidance in the &#8217;Date and Times Data Types&#8217; Proposal.</p>

<h3><a name="_Toc517164403"></a><a name="_Toc79313725"></a>2.5.2<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Positioning within the Model </h3>

<p class=MsoNormal>Despite the form of using a single &#8220;start date&#8221;,
we will for the moment talk about attaching a &#8220;range&#8221; to various
design constructs. The &#8220;range&#8221; should always be a child
(sub-element/attribute) of the object/relationship/attribute it describes;
never a peer. This keeps meaning clear. Further, it applies to the
&#8220;state&#8221; of its containing element, and thus should be considered to
apply equally to all of its peer descriptors, since they simply help describe
the same parent. Note that this means that in order to provide a range for a
particular &#8220;attribute&#8221; of an object, the XML entity construct must
be used.</p>

<p class=MsoNormal>It is highly recommended that an element with a date range
not be designated as the descendent (child, grandchild, etc.) of another
element having a date range. Doing so avoids bounds checking (in theory the
inner range should need to be contained within the containing range.) It also
prevents odd repetition of data of the inner element if the outer element
requires multiple instances to represent states through time. Note that this
may drive design choice to create containers that make different time-lined
entities peers to each other where in other circumstances they would have had a
parent-child relationship. </p>

<p class=MsoNormal>An example of this last situation comes from the benefits
world where there may be a section on employment (position, title, department,
etc.) while there is also information on benefits themselves. The benefits data
could easily be seen as an attribute of the employment information, but we
would propose you create an employee that has repeating entities for both
employment information and benefits information. This allows either segment to
repeat and show state without requiring repetition for the other.</p>

<h3><a name="_Toc517164404"></a><a name="_Toc79313726"></a>2.5.3<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Allowance for Multiple States </h3>

<p class=MsoNormal>If the above guidelines are followed, it should be easy to
indicate in your implementation guide that multiple states are allowed for
elements the directly contain a range, and that the repetition is to be used as
described below to allow for communication of multiple newly discovered states
as well as correction as described below. </p>

<p class=MsoNormal>Unless you are absolutely sure in your design that issues
such as retroactive correction are not an issue, it is typically wise to allow
for multiple representations of state, even if particular trading partners opt
against utilizing such a feature.</p>

<h3><a name="_Toc517164405"></a><a name="_Toc79313727"></a>2.5.4<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Correction </h3>

<p class=xml><span style='font-family:Arial'>Provided multiple states are
allowed in some form, correction is conceptually simple, but may required
difficult coding to implement perfectly. A valid example of any design should
include the ability to list multiple states for a single entity, as a single
&#8220;transaction&#8221;. A correction is then accomplished by finding the
lesser of the oldest date for which state was previously mis-communicated and
the earliest date for which new information should be provided; from this
earliest date, each successive state should be transmitted as well. </span></p>

<p class=xml><span style='font-family:Arial'>Taken to its extreme, this
approach allows for a full validation file to show that two systems are fully
in sync through time.</span></p>

<h2><a name="_Toc517164406"></a><a name="_Toc79313728"></a>2.6<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Providing Implementation Guide Documentation</h2>

<p class=MsoNormal>Future revisions of this document will attempt to provide
&#8220;boiler plate&#8221; descriptions to be placed to describe date elements
in workgroup layouts. For now, take it is a requirement that the expected use
be clearly documented so the desire for consistency of dating nuances between
different layouts is effectively eliminated. For layouts making very high use
of effective dating (Payroll and Benefits Enrollment being obvious examples),
it may be that the best course of action is to refer to this guide directly, in
its entirety.</p>

<span style='font-size:14.0pt;font-family:Copperplate31ab'><br clear=all
style='page-break-before:always'>
</span>

<h1><a name="_Toc517164391"></a><a name="_Toc492656050"></a><a
name="_Toc492655888"></a><a name="_Toc487469954"></a><a name="_Toc480517156"></a><a
name="_Toc459726669"></a><a name="_Toc79313729"></a>3<span style='font-size:
7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Appendix A - Vocabulary Requirements</h1>

<p class=MsoNormal><i>Because of the significant dependence upon the general
concepts of dates and time in effective dating, refer also to the vocabulary
area of the DateTime Data Types. The data types themselves are considered as
part of the vernacular of this document.</i></p>

<h2><a name="_Toc517164392"></a><a name="_Toc79313730"></a>3.1<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Overview</h2>

<p class=MsoNormal>Before covering individual terminology, we must first have
an overall understanding of &#8220;Effective Dating&#8221; and the range of
situations it is frequently meant to entail. Because the specific term
&#8220;Effective Dating&#8221; (or &#8220;Effective Date&#8221;) tends to mean
different things to different people, we will take it to be inclusive of all of
these possible meaning. Thus we will also endeavor to solely use other terms to
describe the specific sub-cases.</p>

<p class=MsoNormal>In the next paragraphs we will examine situations that will
allow us to illustrate various terminology. </p>

<p class=MsoNormal>The dates and times that are included in electronic
transactions can be classified as one of two types, which we will call
&#8220;dating scope&#8221; and &#8220;dating character&#8221;. Consider first
that a date or time is never an object unto itself&#8212;that is we would never
choose to report on the day of 1999-04-22 where we would then describe all of
the attributes of that day. Instead a date or time is always to help us
describe some other object or relationship. &#8220;Dating scope&#8221; refers
to whether what is being described is &#8220;an event&#8221; or &#8220;a
state&#8221;. &#8220;Dating character&#8221; differentiates whether we are
describing an event or state in the &#8220;physical world&#8221; as opposed to
a &#8220;computer system representation&#8221;.</p>

<h3><a name="_Toc517164393"></a><a name="_Toc79313731"></a>3.1.1<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>&#8220;Dating Scope&#8221;</h3>

<p class=MsoNormal>When one considers &#8220;dating scope&#8221;, think of
&#8220;hiring&#8221; and &#8220;termination&#8221; as opposed to
&#8220;employment&#8221;. If one desires to describe the event of hiring a new
employee, one might look at a series of specific events such as interview
dates, the date an offer was extended and/or accepted, and probably most
importantly the first day of work, frequently referred to as the &#8220;hire
date&#8221;. The event &#8220;termination&#8221; usually will have a date and a
reason. These are &#8220;events&#8221; thus &#8220;hire date&#8221; and
&#8220;termination date&#8221; are &#8220;event dates&#8221;.</p>

<p class=MsoNormal>On the other hand, if one discusses
&#8220;employment&#8221;, it will have a start date and possibly an end date.
All description will be an attribute of the employment relationship, with start
and end dates being just two more of those descriptive elements. In this case,
we would refer to employment as a &#8220;state&#8221;, presumably the state of
being employed by a particular company. It could be that the object to describe
the state of employment indicates which division the employee is in, or
alternately an indicator to show that the current &#8220;state&#8221; of the
employee is &#8220;no longer employed&#8221;.</p>

<p class=MsoNormal>In the employment example, two examples are given for the
use of dates, but both are representations of descriptions of
&#8220;state&#8221;. In one, the object describes the employment relationship
and as such should include all information about the relationship, including
dates for both the start and end of the relationship. The other approach is to
represent the employment relationship as a series of
&#8220;point-in-time&#8221; snap shots of the state of the relationship. In
this latter approach there would only be a &#8220;start date&#8221; as the
&#8220;end date&#8221; would be realized as the &#8220;start date&#8221; of a
new &#8220;state&#8221;.</p>

<p class=MsoNormal>An important item to note at this point is that within a
&#8220;state&#8221; approach, the &#8220;start date&#8221; and &#8220;end date&#8221;
(if used) are examples of &#8220;event dates&#8221;. The business goals that
tend to imply the use of one approach over the other are covered in the next
chapter.</p>

<h3><a name="_Toc517164394"></a><a name="_Toc79313732"></a>3.1.2<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>&#8220;Dating Character&#8221;</h3>

<p class=MsoNormal>&#8220;Dating scope&#8221; is the more important
differentiator, but considering the &#8220;dating character&#8221; of the
information you want included can help to make an implementation clearer how an
data element is to be populated. The idea of &#8220;dating character&#8221; is
that information that is collected within an HR system can be categorized in two
ways; information about the &#8220;physical world&#8221;, which can be thought
of as information that would exist even if the HR system did not exist; dates
that are part of the &#8220;computer system representation&#8221; are
constructs imposed by the system itself.</p>

<p class=MsoNormal>The vast majority of date/time information fields in an HR
system are part of the &#8220;physical world&#8221; view. In fact, at a glance,
the only fields that are obviously part of the &#8220;computer system
representation&#8221; are data entry time stamps: record creation and change
dates. The reason it is so important to differentiate these ideas is that since
most designs will expect &#8220;physical world&#8221; dates, it should be made
clear that a timestamp of when information when data entered is not a suitable
substitute.</p>

<p class=MsoNormal>As an example, a performance review was due to occur for a
pay increase to take effect on 2000-09-01. The paperwork for the pay increase
does not arrive at HR until 2000-09-22, but the new pay rate is entered into
the system as soon as it arrives. If a feed were required to a second system to
calculate actual payments, it would be very unfortunate for the timestamp
(2000-09-22) to be used rather than the actual start date (2000-09-01) of the
new pay rate. If the system includes a field to record when the form was
received, this would be seen as &#8220;physical world&#8221; data, but would be
equally inappropriate to use as described.</p>

<p class=MsoNormal>The last part of the above example shows an example of
something that could be (and often is) called a &#8220;transaction date&#8221;.
This term is used as vaguely as &#8220;effective date&#8221; however, so we
choose not to adopt it for use, as it does not tend to clarify meaning.
Specifically, when a &#8220;start date&#8221; is used as an &#8220;event
date&#8221; to represent when a state takes effect, this is also frequently called
the &#8220;transaction date&#8221;<b><i> </i></b>for the data element on a feed
layout.</p>

<h2><a name="_Toc517164395"></a><a name="_Toc79313733"></a>3.2<span
style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Definitions</h2>

<p class=MsoNormal><b>Effective Date/Effective Dating</b> &#8211; A date that
is used, or a practice of using dates, to indicate when events being described
occurred or will occur. These events can include the beginning and ending
points of a period of time for which a particular representation is considered
accurate. Because of the broad nature of this term, it should not be used to
refer to particular data elements; instead use the terms: &#8220;Event
Date&#8221;, &#8220;Start Date&#8221;, and &#8220;End Date&#8221;.</p>

<p class=MsoNormal><b>Dating Scope</b> &#8211; The concept of using dates to
represent discrete occurrences in time (&#8220;Applying to Event&#8221;) as
opposed to indicating a period of time through which a representation of state
is applicable (&#8220;Applying to State&#8221;). See the &#8220;Dating
Scope&#8221; section, above, for more detail.</p>

<p class=MsoNormal><b>Applying to Event</b> &#8211; Applying the use of dates
to represent when a particular event occurred or will occur. See also
&#8220;Dating Scope&#8221;.</p>

<p class=MsoNormal><b>Applying to State</b> &#8211; Applying the use of dates
to represent a period of time through which a described state of an object,
relationship, or attribute is true. See also &#8220;Dating Scope&#8221;</p>

<p class=MsoNormal><b>Dating Character</b> &#8211; The concept of using dates
to represent information in the &#8220;physical world&#8221; as opposed to
information that is part of a &#8220;computer system representation&#8221;. See
the &#8220;Dating Character&#8221; section, above, for more detail.</p>

<p class=MsoNormal><b>Physical World</b> &#8211; A concept applying to data
that is part of the administration of human resources, as opposed to constructs
that only exist because of the presence of a computer system. See also
&#8220;Dating Character&#8221;.</p>

<p class=MsoNormal><b>Computer System Representation</b> &#8211; The opposite
of &#8220;physical world&#8221;. This is Information that exists to suit the
needs of a computer system that would not otherwise exist See also
&#8220;Dating Character&#8221;.</p>

<p class=xml><b><span style='font-family:Arial'>Event Date</span></b><span
style='font-family:Arial'> &#8211; A date used to represent when a particular
event (computer system or physical world) occurred or will occur. XML data
elements that are &#8220;Event Dates&#8221; will be named uniquely to indicate
the event they are describing.</span></p>

<p class=MsoNormal><b>Start Date</b> &#8211; A date used to indicate the first
day (inclusive), or the date and time, for which a particular representation of
state is in force. Any XML data element representing a &#8220;Start Date&#8221;
should be called: <b><i>StartDate</i></b>.</p>

<p class=MsoNormal><b>End Date</b> &#8211; A date used to indicate the last day,
or the date and time, for which a particular representation of state is in
force. It is <i>always</i> to be inclusive. A date used to represent the first
day that a particular state was no longer in force would be a &#8220;Start
Date&#8221; for a new state. Any XML data element representing an &#8220;End
Date&#8221; should be called: <b><i>EndDate</i></b>.</p>

<p class=MsoNormal><b>Transaction Date</b> &#8211; A data element containing a
date that, depending on context, could be an &#8220;Event Date&#8221;,
&#8220;Start Date&#8221;, or &#8220;End Date&#8221;. More discussion is
provided in the &#8220;Data Character&#8221; section, above. Like
&#8220;Effective Date&#8221;, this term is very vague as it is already used in
the industry, so we choose not to use the term.</p>

<p class=MsoNormal><b>Corrective Date</b> &#8211; Sending a value for an
&#8220;Event Date&#8221;, &#8220;Start Date&#8221;, or &#8220;End Date&#8221;
that is intended to correct previously communicated information rather than
provide new information. For an &#8220;Event Date&#8221;, it simply means
sending a new value. How to correct the period of time for which a previously
communicated state should be considered &#8220;in force&#8221; is dependent on
the particular design chosen. This is discussed in Chapter 2 Implementation
Considerations. See also &#8220;Never In Force&#8221;.</p>

<p class=MsoNormal><b>Unbounded</b> &#8211; When a period of time is
&#8220;Unbounded&#8221;, the &#8220;notApplicable&#8221; value is used to
represent this state.&nbsp; Within a period, for a &#8220;Start Date&#8221;, it
represents the beginning of time; for an &#8220;End Date&#8221;, it represents
the end of time. NOTE: When &#8220;notApplicable&#8221; is used to represent a
point in time, its meaning must be made clear, such as &#8220;Deceased
Date&#8221; where it would mean the person is not dead.</p>

<p class=MsoNormal><b>Never In Force/NIF</b> &#8211; A concept to represent
that a previously transmitted state was sent in error, or was subsequently
found to never have occurred. If there is no available representation of state
in the particular design to designate &#8220;no state&#8221; (such as a benefit
plan indicator of &#8220;None&#8221;), the correction must be via a data
element to indicate that the state was &#8220;Never In Force&#8221;. This is
discussed in Chapter 2 Implementation Considerations. See also
&#8220;Corrective Date&#8221;.</p>

<p class=MsoNormal>The following terms are used as described in the <i>DateTime
Data Types</i>: Global</p>

<p class=MsoNormal style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'>&middot;</span><span style='font-size:7.0pt;
font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Local</p>

<p class=MsoNormal style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'>&middot;</span><span style='font-size:7.0pt;
font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Date</p>

<p class=MsoNormal style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'>&middot;</span><span style='font-size:7.0pt;
font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>DateTime</p>

<p class=MsoNormal style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'>&middot;</span><span style='font-size:7.0pt;
font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Not Applicable</p>

<p class=MsoNormal style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'>&middot;</span><span style='font-size:7.0pt;
font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Not Known</p>

<span style='font-size:14.0pt;font-family:Copperplate31ab'><br clear=all
style='page-break-before:always'>
</span>

<h1><a name="_Toc79313734">4</a><span style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Appendix B - Document Version History</h1>

<p class=MsoNormal><span style='color:blue'>&nbsp;</span></p>

<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0
 style='margin-left:-.05in;border-collapse:collapse'>
 <tr>
  <td width=102 valign=top style='width:76.5pt;border:solid windowtext 1.0pt;
  background:#E5E5E5;padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext align=center style='text-align:center'><b>Date</b></p>
  </td>
  <td width=462 valign=top style='width:346.5pt;border:solid windowtext 1.0pt;
  border-left:none;background:#E5E5E5;padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext><b>Description</b></p>
  </td>
 </tr>
 <tr>
  <td width=102 valign=top style='width:76.5pt;border:solid windowtext 1.0pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext align=center style='text-align:center'>2001-02-01</p>
  </td>
  <td width=462 valign=top style='width:346.5pt;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext>Initial Draft </p>
  </td>
 </tr>
 <tr>
  <td width=102 valign=top style='width:76.5pt;border:solid windowtext 1.0pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext align=center style='text-align:center'>2001-05-23</p>
  </td>
  <td width=462 valign=top style='width:346.5pt;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext>Data types and Issue lists removed to separate documents</p>
  </td>
 </tr>
 <tr>
  <td width=102 valign=top style='width:76.5pt;border:solid windowtext 1.0pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext align=center style='text-align:center'>2001-06-03</p>
  </td>
  <td width=462 valign=top style='width:346.5pt;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext>Straw-man for Guideline content. Intended to be last major
  re-org prior to submission for vote.</p>
  </td>
 </tr>
 <tr>
  <td width=102 valign=top style='width:76.5pt;border:solid windowtext 1.0pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext align=center style='text-align:center'>2001-06-14</p>
  </td>
  <td width=462 valign=top style='width:346.5pt;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext>Everything except resolving discrepancies with data type
  doc</p>
  </td>
 </tr>
 <tr>
  <td width=102 valign=top style='width:76.5pt;border:solid windowtext 1.0pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext align=center style='text-align:center'>2001-06-25</p>
  </td>
  <td width=462 valign=top style='width:346.5pt;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext>Copy approved for distribution by CPO</p>
  </td>
 </tr>
 <tr>
  <td width=102 valign=top style='width:76.5pt;border:solid windowtext 1.0pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext align=center style='text-align:center'>2001-07-20</p>
  </td>
  <td width=462 valign=top style='width:346.5pt;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext>Recommendation approved by HR-XML Consortium</p>
  </td>
 </tr>
 <tr>
  <td width=102 valign=top style='width:76.5pt;border:solid windowtext 1.0pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext align=center style='text-align:center'>2003-Feb-26</p>
  </td>
  <td width=462 valign=top style='width:346.5pt;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext>Approved recommendation by HR-XML Consortium. <span
  style='background:white'>The default and targetNamespaces of all HR-XML
  schemas have been standardized.</span> This recommendation is available as
  part of the HR-XML 2_0 architecture.</p>
  </td>
 </tr>
 <tr>
  <td width=102 valign=top style='width:76.5pt;border:solid windowtext 1.0pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext align=center style='text-align:center'>2006-Feb-28</p>
  </td>
  <td width=462 valign=top style='width:346.5pt;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext>Approved by Consortium</p>
  </td>
 </tr>
 <tr>
  <td width=102 valign=top style='width:76.5pt;border:solid windowtext 1.0pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext align=center style='text-align:center'>2007-Apr-15</p>
  </td>
  <td width=462 valign=top style='width:346.5pt;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=tabletext>Approved by Consortium</p>
  </td>
 </tr>
</table>

<h1><a name="_Toc79313735">5</a><span style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Appendix C &#8211; Related Documents</h1>

<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=606
 style='width:454.5pt;margin-left:-.05in;border-collapse:collapse'>
 <tr style='height:13.95pt'>
  <td width=216 valign=top style='width:2.25in;background:#E5E5E5;padding:0in 5.4pt 0in 5.4pt;
  height:13.95pt'>
  <p class=tabletext><b>Reference</b></p>
  </td>
  <td width=390 valign=top style='width:292.5pt;background:#E5E5E5;padding:
  0in 5.4pt 0in 5.4pt;height:13.95pt'>
  <p class=tabletext><b>Link</b></p>
  </td>
 </tr>
 <tr style='height:14.85pt'>
  <td width=216 valign=top style='width:2.25in;padding:0in 5.4pt 0in 5.4pt;
  height:14.85pt'>
  <p class=tabletext>&nbsp;HR-XML DateTime Data Types</p>
  </td>
  <td width=390 valign=top style='width:292.5pt;padding:0in 5.4pt 0in 5.4pt;
  height:14.85pt'>
  <p class=tabletext0><span style='font-size:9.0pt'><a
  href="http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/DateTimeDataTypes.html">http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/DateTimeDataTypes.html</a></span></p>
  </td>
 </tr>
 <tr style='height:14.85pt'>
  <td width=216 valign=top style='width:2.25in;padding:0in 5.4pt 0in 5.4pt;
  height:14.85pt'>
  <p class=tabletext>XML Schema Part 0: Primer</p>
  </td>
  <td width=390 valign=top style='width:292.5pt;padding:0in 5.4pt 0in 5.4pt;
  height:14.85pt'>
  <p class=tabletext><span style='font-size:9.0pt;color:blue'>http://www.w3.org/TR/xmlSchema-0/</span></p>
  </td>
 </tr>
 <tr style='height:14.85pt'>
  <td width=216 valign=top style='width:2.25in;padding:0in 5.4pt 0in 5.4pt;
  height:14.85pt'>
  <p class=tabletext>XML Schema Part 2: Datatypes</p>
  </td>
  <td width=390 valign=top style='width:292.5pt;padding:0in 5.4pt 0in 5.4pt;
  height:14.85pt'>
  <p class=tabletext><span style='font-size:9.0pt;color:blue'>http://www.w3.org/TR/xmlSchema-2/</span></p>
  </td>
 </tr>
</table>

<h1 style='margin-left:0in;text-indent:0in'>&nbsp;</h1>

<span style='font-size:14.0pt;font-family:Copperplate31ab'><br clear=all
style='page-break-before:always'>
</span>

<h1><a name="_Toc79313736">6</a><span style='font-size:7.0pt;font-family:"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Appendix C &#8211; Reference Examples</h1>

<p class=h4 style='margin:0in;margin-bottom:.0001pt'><span style='font-family:
"Arial Black";font-weight:normal'>Sample Schema Design:</span></p>

<p class=h4><span style='font-family:"Arial Black";font-weight:normal'><img
border=0 width=605 height=284 src="EffectiveDating_files/image002.jpg"></span></p>

<p class=h4 style='margin:0in;margin-bottom:.0001pt'><span style='font-family:
"Arial Black";font-weight:normal'>&nbsp;</span></p>

<p class=h4 style='margin:0in;margin-bottom:.0001pt'><span style='font-family:
"Arial Black";font-weight:normal'>Sample Schema</span></p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&lt;?xml version =
&quot;1.0&quot; encoding = &quot;UTF-8&quot;?&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&lt;xsd:schema xmlns =
&quot;d:\cpotest\cpoDateTimeTypesTest.xsd&quot;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;
&nbsp;targetNamespace = &quot;d:\cpotest\cpoDateTimeTypesTest.xsd&quot;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;
&nbsp;xmlns:xsd = &quot;http://www.w3.org/2000/10/XMLSchema&quot;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;
&nbsp;elementFormDefault = &quot;qualified&quot;&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp; &lt;xsd:include
schemaLocation = &quot;cpoDateTimeTypes-2001-06-12.xsd&quot;/&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;
&lt;xsd:element name = &quot;BusinessContext&quot;&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;
&lt;xsd:complexType&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;xsd:sequence&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;xsd:element ref = &quot;Employee&quot; maxOccurs =
&quot;unbounded&quot;/&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;/xsd:sequence&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;
&lt;/xsd:complexType&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;
&lt;/xsd:element&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;
&lt;xsd:element name = &quot;Employee&quot;&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;
&lt;xsd:complexType&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;xsd:sequence&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;xsd:element name = &quot;Comments&quot; type = &quot;xsd:string&quot;/&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;xsd:element name = &quot;HireDate&quot; type = &quot;DateType&quot;/&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;xsd:element name = &quot;TermDate&quot; type =
&quot;DateNkNaType&quot;/&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;xsd:element name = &quot;TransactionDate&quot; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp; type = &quot;DateTimeType&quot;/&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;/xsd:sequence&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;xsd:attribute name = &quot;startDate&quot; use = &quot;required&quot; </p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;type = &quot;DateNkType&quot;/&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;xsd:attribute name = &quot;endDate&quot; use = &quot;required&quot; </p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;type = &quot;xsd:string&quot;/&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;
&lt;/xsd:complexType&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp; <span
lang=NL>&lt;/xsd:element&gt;</span></p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'><span lang=NL>&lt;/xsd:schema&gt;</span></p>

<p class=h4><span lang=NL style='font-family:"Arial Black";font-weight:normal'>Sample
Valid XML Document</span></p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&lt;?xml version =
&quot;1.0&quot; encoding = &quot;UTF-8&quot;?&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&lt;BusinessContext
xmlns:xsi = &quot;http://www.w3.org/2000/10/XMLSchema-instance&quot;
xsi:noNamespaceSchemaLocation = &quot;DateTimeTypes.xsd&quot;&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp; &lt;Employee
startDate = &quot;2001-04-05&quot; endDate = &quot;notApplicable&quot;&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;
&lt;HireDate&gt;2001-04-01&lt;/HireDate&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp; <span
lang=FR>&lt;TermDate&gt;notApplicable&lt;/TermDate&gt;</span></p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'><span lang=FR>&nbsp;&nbsp;&nbsp;&nbsp;
&lt;TransactionDate&gt;2001-04-18T04:05:32&lt;/TransactionDate&gt;</span></p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'><span lang=FR>&nbsp;&nbsp;
</span>&lt;/Employee&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp; &lt;Employee
startDate = &quot;notKnown&quot; endDate = &quot;2001-04-30&quot;&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;
&lt;HireDate&gt;2001-02-01&lt;/HireDate&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;
&lt;TermDate&gt;2001-04-30&lt;/TermDate&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;&nbsp;&nbsp;
&lt;TransactionDate&gt;2001-04-18T04:05:32-05:00&lt;/TransactionDate&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&nbsp;&nbsp;
&lt;/Employee&gt;</p>

<p class=xml style='margin:0in;margin-bottom:.0001pt'>&lt;/BusinessContext&gt;</p>

<p class=xml><span style='font-family:Arial'>&nbsp;</span></p>

</div>

</body>

</html>
